|
In software engineering, service virtualization is a method to emulate the behavior of specific components in heterogeneous component-based applications such as API-driven applications, cloud-based applications and service-oriented architectures. It is used to provide software development and QA/testing teams access to dependent system components that are needed to exercise an application under test (AUT), but are unavailable or difficult-to-access for development and testing purposes. With the behavior of the dependent components "virtualized," testing and development can proceed without accessing the actual live components. Service virtualization is recognized by vendors, industry analysts, and industry publications as being different than mocking.〔(Service Virtualization as an Alternative to Mocking ), by Jonathan Allen, eBizQ April 22, 2013〕〔 ==Service virtualization overview== Service virtualization emulates the behavior of software components to remove dependency constraints on development and testing teams. Such constraints occur in complex, interdependent environments when a component connected to the application under test is: * Not yet completed * Still evolving * Controlled by a third-party or partner * Available for testing only in limited capacity or at inconvenient times * Difficult to provision or configure in a test environment * Needed for simultaneous access by different teams with varied test data setup and other requirements * Restricted or costly to use for load and performance testing 〔(Service Virtualization for Modern Applications ) by Gaurish Hattangadi, Virtual Strategy Magazine, November 28, 2010〕 Although the term "service virtualization" reflects the technique's initial focus on virtualizing web services, service virtualization extends across all aspects of composite applications: services, databases, mainframes, ESBs, and other components that communicate using common messaging protocols.〔( Managing Test Environments ) by Liz McMillan, Cloud Computing Journal, December 2011〕〔(Application Behavior Virtualization ) by Elizabeth White, Cloud Computing Journal, December 2011〕〔(Database Virtualization For Development and Test ) by Wayne Ariola, ST & QA Magazine, March 2012〕 Service virtualization emulates only the behavior of the specific dependent components that developers or testers need to exercise in order to complete their end-to-end transactions. Rather than virtualizing entire systems, it virtualizes only specific slices of dependent behavior critical to the execution of development and testing tasks. This provides just enough application logic so that the developers or testers get what they need without having to wait for the actual service to be completed and readily available. For instance, instead of virtualizing an entire database (and performing all associated test data management as well as setting up the database for every test session), you monitor how the application interacts with the database, then you emulate the related database behavior (the SQL queries that are passed to the database, the corresponding result sets that are returned, and so forth).〔(An Intro to SOA and Virtualization ) by John Michelsen, WebServices.org, August 2007〕 〔(The Next Generation of Test Environment Management ) by Wayne Ariola, Virtualization Journal, July 12, 2011〕 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「service virtualization」の詳細全文を読む スポンサード リンク
|